Each collaborating vault should have two export tasks scheduled to run on a regular basis: one to run daily and synchronize other vaults with normal priority changes and one to run more frequently to synchronize user-initiated, high priority transfers. The only differences in the configuration of the tasks is the command line parameters and the frequency in which they are run.
The normal priority export task runs the Meridian Enterprise export processor to create briefcases for remote collaborating sites. A parameter in the command line of the task specifies which transfers to process.
The normal priority command line should specify the following parameters:
If the configuration file is located in the same folder as the vault export processor, the path can be omitted.
Note Installing the processors as described in Installing the GCF components installs sample .cmd files for export and import with the correct configuration file names and share names that you can use to compose the command line.
Following is an example of a normal priority Meridian Enterprise export processor command line:
"C:\GCF\Meridian\Processors\GCFExportLauncher.exe" GCFProc.ini Scheduled
The high priority export task only processes those transfers that are initiated directly by users, such as: enlisting a vault, transferring or claiming ownership, and requesting immediate distribution.
This task should be scheduled to run more frequently to process these transfers. We recommend a schedule interval between 10 minutes and 1 hour. However, the interval for this task should not be an even fraction of the normal priority task interval so that the two tasks will not start at the same time. For example, if the normal priority task interval is every 240 minutes, the high priority task interval should not be 15 or 16, but 17 minutes.
The overhead for running the task when no work needs to be done is small. The Meridian Enterprise export processor only needs to check a few records in a Meridian Enterprise table.
The high priority task command line should have only one argument, which is the name of the configuration file. If the configuration file is located in the same folder as GCFExportLauncher.exe, the path can be omitted.
Following is an example of an immediate export task command line:
"C:\GCF\Meridian\Processors\GCFExportLauncher.exe" GCFProc.ini
Note On 64-bit operating systems, multiple instances of GCFExportProc.exe can exist for the same target share. The export processor starts and fails to find an existing instance. This can occur only when GCFExportLauncher.exe is used to export to all available shares.
To work around this issue, instead of scheduling two export tasks (one for scheduled execution and one for immediate execution), schedule two tasks for each destination share name. For example, assuming three GCF sites: SiteA, SiteB, and SiteC synchronized by two tasks with command lines similar to the following:
GCFExportLauncher.exe gcf.ini scheduled GCFExportLauncher.exe gcf.ini
Replace them with four tasks for each site with command lines similar to the following:
GCFExportProc.exe gcf.ini SiteB true GCFExportProc.exe gcf.ini SiteC true GCFExportProc.exe gcf.ini SiteB false GCFExportProc.exe gcf.ini SiteC false
The first two tasks perform SiteA scheduled updates, the second two tasks perform SiteA immediate updates. Create four similar tasks on each of SiteB and SiteC.
You can also prevent unnecessary instances by selecting the Do not start a new instance rule in the task settings.